Telematics system

ABSTRACT

Some embodiments of the invention concern a novel and interactive way to deliver telematics solutions by separating the delivery of the hardware and software component of a telematics device. The software telematics application is selected and delivered to the customer&#39;s telematics device by in-application purchases via the customer&#39;s mobile device. The mobile device contains a user interface that is adapted to control and configure the telematics device. The customers may upgrade their telematics applications using their mobile devices. A retailer may also request the upgrade of a customer&#39;s telematics application using the retailer&#39;s mobile device. The user interface also provide a customer profiler tool to provide individualized search results and recommend telematics applications based on the customer&#39;s profile.

This application is a continuation of application Ser. No. 15/058,945,filed on Mar. 2, 2016, which claims priory from Provisional ApplicationNo. 62/134,368, filed on Mar. 17, 2015, the content of which isincorporated by reference in its entirety.

FIELD OF THE INVENTION

The present invention relates to aftermarket technologies in vehicles.In particular, the present invention relates to delivering aftermarkettelematics solutions to different vehicles.

BACKGROUND

Telematics is an interdisciplinary field that utilizes integrated use oftelecommunications and informatics for application in vehicles.Typically, a telematics feature in a vehicle could be any technologiesthat are related to sending, receiving and storing information ofvehicles. Common telematics features available on the market includevehicle remote start control, security features such as unauthorizedentry alerts and starter disable, owner's recognition settings, GPSnavigation system, keyless entry, climate control seat activationadjustment, roadside assistance, vehicle diagnostic information, vehicleinformation monitoring and indication, subscription to vehicle warrantynotification, dynamic traction control alerts with repair estimates,processors for replacement radio and stereo system, etc.

A telematics feature can be included as an OEM (original equipmentmanufacturer) feature or as an aftermarket addition to the vehicle. Forexample, luxurious vehicles often include GPS navigation systems as anOEM feature that comes with the vehicles at purchase. However, forvehicles that do not come with GPS navigation systems, owners may alsopurchase aftermarket GPS navigation systems as aftermarket products tobe installed in their vehicles.

A telematics solution is usually provided to the end user based on itsfeature. Hardware and software of a telematics device are deliveredtogether with fixed or limited expandable functionalities. For example,if a car owner would like to add a navigation system to his vehicle, thecurrent option is to purchase an aftermarket GPS navigation system thathas software preloaded in the GPS system. The GPS system usuallycontains relatively fixed functionalities. It is very difficult for theowner to upgrade his GPS system to add any other telematics featuresthat are not included in the GPS system's design. In other words, if theGPS system is not designed to perform vehicle diagnostic tests, it willbe very difficult for the owner to upgrade the GPS system to includefeatures that perform vehicle diagnoses. The owner will have to purchaseanother aftermarket telematics device that performs vehicle diagnosisand have the device installed in his vehicle. Likewise, the newaftermarket telematics device that performs vehicle diagnoses usuallyalso has limited expandable functionalities and cannot be upgraded toperform other telematics features such as remote entry.

Such limited functionalities of current aftermarket telematics devicesare inconvenient to the end users, particularly when most telematicsdevices are installed and mounted in vehicles in a relatively permanentfashion. For examples, many telematics devices are located either behindthe central console or at the head unit. In addition, the installationof most telematics devices is time consuming and requires particularexpertise. Hence, for car owners to add any telematics features to theirvehicles, they often are required to bring their vehicles to specificretailers that have the expertise to install additional devices. Thiscurrent way to add telematics features to vehicles is inflexible andnon-interactive.

SUMMARY

It is an objective of the present invention to provide a flexible andinteractive approach to offer different telematics solutions. It is alsoan objective of the present invention to provide convenient ways forcustomers to choose and upgrade their telematics devices. It is alsoanother objective of the present invention to provide an individualizedsolution to customers based on their needs.

In one embodiment of the present invention, the embodiment is a systemthat delivers different telematics solutions to customers. The systemcomprises a data source linked to a server, a first customer userinterface installed in a first customer mobile device, a secondintermediary user interface installed in a second intermediary mobiledevice, a third intermediary user interface installed in a thirdintermediary mobile device, an aftermarket telematics device installedin a vehicle, and a potential add-on component with the aftermarkettelematics device. The aftermarket telematics device is controlled by atleast one telematics application and is compatible with a plurality oftelematics applications.

The aftermarket telematics device comprises a storage medium, atransceiver that is adapted to communicate with a plurality of mobiledevices. The storage medium contains instructions such that theaftermarket telematics device is configurable to be associated withdifferent mobile devices. The aftermarket telematics device is adaptedto receive telematics applications from the mobile devices. Also, theaftermarket telematics device is adapted to collect data from thevehicle and transmit the data to the mobile devices. After a telematicsapplication is installed in the aftermarket telematics device, thevehicle owner may use the first customer user interface installed in hismobile device to control and configure the aftermarket telematicsdevice.

After an aftermarket telematics device is sold to a customer, telematicsapplications that are compatible with the aftermarket telematics devicecan be delivered to the customer in different ways. In one scenario, acustomer purchases an aftermarket telematics device, but a retailer isresponsible for installing the aftermarket telematics device. Thedelivery of a particular telematics application is achieved throughseveral separate steps. First, the retailer may use a secondintermediary mobile device such as a laptop computer to request aparticular telematics application that suits the customer's need. Thedata source is adapted to respond to such request from the secondintermediary user interface. Upon proper authentication by the datasource for an association between the second intermediary user interfaceand the aftermarket telematics device, the data source transmits theparticular telematics application to the laptop computer and transmitsan instruction that will cause the laptop computer to re-transmit theparticular telematics application from the laptop computer to theaftermarket telematics device. The retailer may then connect his laptopcomputer to the aftermarket telematics device via a USB cable. Uponproper authentication, the particular telematics application will bere-transmitted from the laptop computer to the aftermarket telematicsdevice. After the telematics application is installed in the aftermarkettelematics device, the delivery of the telematics solution is complete.In some situations, the telematics application is first temporarilystored in the laptop computer, then the laptop computer to re-transmitthe particular telematics application to the aftermarket telematicsdevice when the laptop computer is in proximity of the aftermarkettelematics device.

In another scenario, a customer has a functional aftermarket telematicsdevice already installed in his vehicle, but he wants to upgrade theaftermarket telematics device. The customer prefers to ask a retailerfor assistance. An embodiment of the present invention provides a novelway to deliver a new telematics application without requiring thecustomer to drive his vehicle back to the retailer to perform bothhardware and software upgrade. In this particular scenario, the datasource, the aftermarket telematics device, the first customer userinterface, and the second intermediary user interface are firstassociated together and authenticated. The first customer user interfaceshares the vehicle's information, the customer's profile, and otherinformation from the aftermarket telematics device with the data source.The data source then shares the same information with the secondintermediary user interface so that the retailer may review suchinformation using the second intermediary user interface. Subsequently,the retailer selects and requests a particular telematics application toupgrade the customer's aftermarket telematics device. The customer isnot required to physically return to the retailer to perform theupgrade. Upon receiving the request from the retailer, the data sourcetransmits the particular telematics application to the customer's firstcustomer mobile device, instead of the second intermediary mobile devicethat is possessed by the retailer. The server also transmits aninstruction that is designed to cause the first customer mobile deviceto re-transmit the particular telematics application to the aftermarkettelematics device. The re-transmission of the telematics application mayoccur when the first customer mobile device is paired with theaftermarket telematics device using a short-range wireless connectionsuch as Bluetooth or when the first customer mobile device is connectedto the aftermarket telematics device via a USB cable. As such, thedelivery of the particular telematics application can be achieved whenthe retailer is away from the customer or the customer's vehicle. Inother words, the particular telematics application is first transmittedto the customer's mobile device upon the retailer's remote request, andthen re-transmitted to the aftermarket telematics device.

In yet another scenario, the customer also wants to upgrade hisaftermarket telematics device, but the telematics feature he wantsrequires an upgrade of the hardware. For example, the hardware of theaftermarket telematics device only supports remote start functionality,but the customer wants to add a GPS navigation system to his vehicle. Inthis case, the customer first purchases a piece of add-on hardware fromthe retailer and connects the add-on to the aftermarket telematicsdevice. Since the additional hardware is provided to the customer as anadd-on, the installation is much simpler than installations that requirecustomers purchase a new telematics device. After the add-on isconnected, the customer may select a particular telematics applicationfor the add-on hardware manually or using the first customer userinterface's recommendations. The retailer who sold the add-on may alsorequest a particular telematics application for the customer.

According to an embodiment of the present invention, the embodimentprovides a customer profiler tool that recommends different telematicsapplications to the customer. The first customer user interface isadapted to collect information such as different search parameters fromcustomers. In the customer profiler tool, the first customer userinterface requires customers to input their email and allows thecustomers to input additional information such as their name, telephonenumbers and address. Then the customer profiler tool continues tocollect additional profile information such as their gender, age, ZIPcode, mobile device, and the mileage of their vehicle.

Based on the information collected, the user interface, working with thedata source, generates a profile that recommends certain telematicsapplications selected from the plurality of different telematicsapplications stored in the data source. The interface will first filterresults by supported vehicle features and then by most suitable featuresfor the customer based on the search parameters collected. The customersmay select any of the telematics applications listed and have thetelematics applications to be delivered to their aftermarket telematicsdevice.

In some embodiments, a cloud service environment is setup to enhance theresults by cross referencing the user's input with statistics thatinclude vehicle warranty status and location-based variables such ascrime rates, climate patterns, fuel costs, average income, and legaldriving age in order to return potential features of interest. The datasource analyzes the customer profile information collected and thestatistics cross-referenced using fuzzy logic and provides properrecommendations to the customer.

Through the customer profiler tool, embodiments of the present inventionprovide an interactive point of sales tool for both the customers andthe retailers to determine the most suitable solution for a particularvehicle based on the customers' preference. This provides anindividualized solution for each customer based on his needs. Thecustomer profiler tool provides recommended telematics application basedon the vehicle condition and the customer's lifestyle. For example, whena customer inputs a ZIP code that has a high crime rate, the customerprofiler tool will analyze the ZIP code and recommend security featuressuch as remote start and GPS tracking to the customer. When anothercustomer inputs a ZIP code that has a high household income and thevehicle is identified is a luxurious vehicle, the customer profilertool, using fuzzy logic generator, will recommend premium telematicsapplications that provide better services.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram representing the parties involved in adelivery of a telematics solution from a manufacturer to a customer inaccordance with an embodiment of the present invention.

FIG. 2 is a schematic representation of a system of telematics featuresin accordance with an embodiment of the present invention.

FIG. 3 is an illustrative representation of an aftermarket telematicsdevice installed in a vehicle and the interaction between the user usinghis mobile device and the telematics device in accordance with anembodiment of the present invention.

FIG. 4 is an illustrative view of some example views of an userinterface in accordance with some embodiments of the present invention.

FIG. 5 is an illustrative view of some example views of an userinterface in accordance with some embodiments of the present invention.

FIG. 6 is an illustrative view of some example views of an userinterface in accordance with some embodiments of the present invention.

FIG. 7 is an illustrative view of some example views of an userinterface in accordance with some embodiments of the present invention.

FIG. 8 is an illustrative view of some example views of an userinterface in accordance with some embodiments of the present invention.

FIG. 9 is an illustrative view of some example views of an userinterface in accordance with some embodiments of the present invention.

FIG. 10 is an illustrative view of some example views of an userinterface in accordance with some embodiments of the present invention.

FIG. 11 is an illustrative view of some example views of an userinterface in accordance with some embodiments of the present invention.

FIG. 12 is an illustrative view of some example views of an userinterface in accordance with some embodiments of the present invention.

FIG. 13 is an illustrative view of some example views of an userinterface in accordance with some embodiments of the present invention.

DETAILED DESCRIPTION OF EMBODIMENTS

The following description is made for the purpose of illustrating thegeneral principles of the invention and should not be taken in alimiting sense. The scope of the invention is best determined byreference to the appended claims.

The invention now will be described more fully hereinafter withreference to the accompanying drawings, in which embodiments of theinvention are shown. This invention may, however, be embodied in manydifferent forms and should not be construed as limited to theembodiments set forth herein. Rather, these embodiments are provided sothat this disclosure will be thorough and complete, and will fullyconvey the scope of the invention to those skilled in the art.

Exemplary embodiments of the present invention are described herein withreference to idealized embodiments of the present invention. As such,variations from the shapes of the illustrations as a result, forexample, of manufacturing techniques and/or tolerances, are to beexpected. Thus, embodiments of the present invention should not beconstrued as limited to the particular shapes of regions illustratedherein but are to include deviations in shapes that result, for example,from manufacturing.

Referring to FIG. 1, it is a schematic representation of the partiesinvolved in a delivery of a telematics solution from a manufacturer to acustomer in accordance with an embodiment of the present invention. Theparties involved in this transaction include a manufacturer 100, anintermediary 102, another intermediary 104, a customer 106 and thirdparty developers 108. The intermediaries shown in FIG. 1 representintermediate parties between the manufacturer 100 and the customer 106when an aftermarket telematics device is sold to the customer 106. In aparticular embodiment, the intermediary 102 is a distributor whopurchases aftermarket telematics devices directly from the manufacturesin quantities and the intermediary 104 is a retailer who purchasesaftermarket telematics devices from the distributor and sellsaftermarket telematics devices to the customers 106.

FIG. 1 illustrates the difference in delivering the hardware component150 and the software component 250 of a telematics solution from themanufacturer 100 to the customer 106 in accordance with an embodiment ofthe present invention. With respect to the hardware component 150 suchas an aftermarket telematics device and an add-on part, it is designedand manufactured by the manufacturer 100. The manufacturer 100 thendelivers the hardware component 150 to the customer 106 via one or morethan one intermediaries 102 and 104. With respect to the softwarecomponent 250 such as a telematics application, it is usually designedand developed by the manufacturer 100. Instead of going through theintermediaries, the software component 250 is directly delivered to thecustomer 106 via remote means that will be discussed in further detailbelow. In some embodiments, the manufacturer 100 discloses the hardwarespecification of the aftermarket telematics devices to limited thirdparty developers 108 for the developers 108 to develop telematicsapplications 250 that are compatible with the hardware component 150.After the telematics applications 250 are developed, they are uploadedto a server and are then directly delivered to the customer 106 viaremote means that will be discussed in further detail below. In otherembodiments, the manufacturer 100 provides an open source environment toallow any third party developers 108 to develop telematics applications250 that are compatible with the manufacturer's aftermarket telematicsdevices.

Referring now to FIG. 2, it is a schematic representation of a system todeliver telematics solution to a customer 106 in accordance with anembodiment of the present invention. The system comprises a data source200 linked to a server 202, a first customer user interface 204installed in a first customer mobile device 206, a second intermediaryuser interface 208 installed in a second intermediary mobile device 210,a third intermediary user interface 222 installed in a thirdintermediary mobile device 212, an aftermarket telematics device 214installed in a vehicle 218, and a potential add-on component 220 linkedto the aftermarket telematics device 214. The aftermarket telematicsdevice 214 is controlled by at least one telematics application 250 andis compatible with a plurality of telematics applications 250. Accordingto some preferred embodiments, the data source 200 is associated with asoftware application platform that is maintained by a manufacturer 100.As such, the manufacturer 100 controls the development, quality,availability and delivery of any telematics applications 250 availableon the data source 200. The data source 200 is linked to the server 202,which stores a plurality of telematics applications 250 that arecompatible with the aftermarket telematics devices 214. Preferably, theserver 202 is a cloud-based server.

The aftermarket telematics device 214 is capable of working with aplurality of telematics applications 250. The aftermarket telematicsdevice 214 comprises a storage medium, a transceiver that is adapted tocommunicate with a plurality of mobile devices 206, 210, and 212 viaprotocols such as Bluetooth, Wi-Fi, and/or USB cable. The storage mediumcontains instructions such that the aftermarket telematics device isconfigurable to be associated with the mobile devices 206, 210, and 212.The aftermarket telematics device 214 is adapted to receive telematicsapplications 250 from the mobile devices 206, 210, and 212 after themobile devices are associated with the aftermarket telematics device214. Also, the aftermarket telematics device 214 is adapted to collectdata from the vehicle 218 and transmit the data to the mobile devices206, 210, and 212 associated with the telematics device 214. After atelematics application 250 is installed in the aftermarket telematicsdevice 214, the first customer user interface 204 can be used to controland configure the aftermarket telematics device 214 in a manner to bediscussed in further details below.

In some embodiments, the manufacturer 100 provides an applicationprogram interface (API) 240 for an open developer environment to allowthird party developers to utilize the application program interface 240to develop third party telematics applications 250. The availability ofthird party applications allows customers 106 to use the telematicsdevices 214 for features that are beyond what the manufacturer 100originally designs. At least four data points and sources are availableto the third party developers 108 to develop telematics applications250. First, vehicle data for the vehicle 218, including data businformation such as OBDII data and other CAN enabled controls, areavailable. Second, there can be a cloud server for vehicle warrantyinformation, demographics and weather. Third, data are also availablefor applications or interfaces used in the mobile devices 206, 210, and212. Fourth, a data point can be found for different OEM applicationprogram interfaces that are offered by the automakers. Developers 108may choose from the different data buckets to develop applications thatcan be purchased by the customers 106 using an in-app purchasing featureof the first customer user interface 204 as discussed in further detailbelow.

In one embodiment, the server 202 is maintained and controlled by themanufacturer 100. In this regard, customers 106 may go to a website oran application store that is maintained by the manufacturer 100 toselect telematics applications 250 that are available for theiraftermarket telematics devices 214. The application store is also theprimary marketplace for third party telematics applications.

Alternative, the server 202 is maintained by a third party and customers106 may go to a third party application store to select telematicsapplications for their aftermarket telematics devices 214. For example,the third party application store could be Google® Play or Apple® AppStore.

In some embodiments, the data source 200 is adapted to communicate withany number of different user interfaces 204, 208, and 222. While twointermediary user interfaces 208 and 222 are shown in the particularembodiment of FIG. 2, there could be any number of intermediary userinterfaces. Preferably, the user interfaces 204, 208, and 222 areprovided and transmitted by the manufacturer 100. For example, the userinterfaces 204, 208, and 222 could be manufacturer's 100 softwareapplications that are installed in different mobile devices 206, 210,212.

Through the mobile devices 206, 210, 212, the users 102, 104, and 106can interact with the data source 200 and control the aftermarkettelematics device 214. In a particular embodiment, the user interfaces204, 208, and 222 communicate with the data source 200 via long-rangedcommunication protocol such as the Internet or wireless 4G network. Onthe other hand, the interfaces 204, 208, and 222 communicate with theaftermarket telematics device 214 with short-ranged protocol such asBluetooth, Wi-Fi, and/or USB cable between a pairing of the aftermarkettelematics device 214 and the mobile devices 206, 210, 212.

The differences of the user interfaces 204, 208, and 222 are mainlybased on their end users. In the particular embodiment shown in FIG. 2,the end user of the first customer user interface 204 is the customer106 who purchased an aftermarket telematics device 214 that is installedin the customer's 106 vehicle 218. The first customer user interface 204is installed in the first customer mobile device 206, which is a mobiledevice possessed by the customer 106. It is noteworthy that thoseskilled in the art would understand that the term mobile device here isnot limited to a smart phone or tablet. It could also refer to anycomputer, such as a laptop or even a desktop computer, or otherelectronic device.

In the particular embodiment shown in FIG. 2, the end user of the secondintermediary user interface 208 is a retailer 104 who sold theaftermarket telematics device 214 to the customer 106. The secondintermediary user interface 208 is installed in the second intermediarymobile device 210 that is used by the retailer 104. The secondintermediary mobile device 210 could be the retailer's 104 mobile phone,tablet, computer, or other similar electronics device at the retailer's104 store. Likewise, the end user of the third intermediary userinterface 222 is a distributor 102 who distributes aftermarkettelematics devices 214 from the manufacturer 100 to the retailer 104.

In one embodiment, the first customer user interface 204 is configurableto be associated with the aftermarket telematics device 214. Preferably,each aftermarket telematics device 214 made by the manufacturer 100 isassigned with a specific and unique identifier. The identifier could bea serial number of the aftermarket telematics device 214. When thecustomer 106 purchases the aftermarket telematics device 214, thecustomer 106 may also download the first customer user interface 204 andinstall the user interface 204 in the customer's 106 mobile device 206.The identifier information of the aftermarket telematics device 214 isthen input into the first customer user interface 204 when theaftermarket telematics device 214 and the first customer user interface204 begin to establish a connection. Once the appropriate identifierinformation is input and is authenticated, the first customer userinterface 204 is associated with the aftermarket telematics device 214in this authentication process. Now the customer 106 may interact withthe aftermarket telematics device 214 via the first customer userinterface 204 in different manners that will be discussed in greaterdetail below.

In some embodiments, a retailer 104 obtains the right to sellaftermarket telematics devices 214 from the manufacturer 100 or througha distributor 102. Once the retailer 104 becomes an authorized dealer tosell the aftermarket telematics devices 214, the manufacturer 100provides and transmits a second intermediary user interface 208 to theretailer 104. In a preferred embodiment, the manufacturer 100 will alsoprovide and deliver second intermediary mobile device(s) 210 to theretailer 104. For example, when the retailer 104 becomes an authorizeddealer for the manufacturer 100, the manufacturer 100 will provide theretailer 104 with a number of second intermediary mobile devices 210,including a desktop computer, a tablet with a credit card swipe tool, asmartphone accessory with transaction capacity plug in. In thissituation, the second intermediary user interface 208 is pre-installedin the second intermediary mobile devices 210.

After the retailer 104 becomes an authorized retailer, the secondintermediary user interface 208 is configurable to be associated withthe aftermarket telematics device 214. When the retailer 104 receives anumber of aftermarket telematics devices 214 from a distributor 102, theaftermarket telematics devices 214 are associated with the secondintermediary user interface 208 using the identifier. When the retailer104 sells a particular aftermarket telematics device 214 to a customer106, the transaction is recorded by the second intermediary userinterface 208 and the unique identifier of the particular aftermarkettelematics device 214 is associated with the transaction. The secondintermediary user interface 208 transmits the transaction and theidentifier to the data source 200 so that the data source 200 mayrecord, verify and authenticate the transaction and the identifier. Now,after the second intermediary user interface 208 is associated with theparticular aftermarket telematics device 214, the data source 200 willhave a record that the retailer 104 is also associated with the customer106 who purchased the particular aftermarket telematics device 214.

The third intermediary user interface 222 is also configurable to beassociated with the aftermarket telematics device 214 in a similarfashion described in the preceding paragraph. Typically, the thirdintermediary user interface 222 is controlled by a distributor 102. Whenthe distributor 102 distributes aftermarket telematics devices 214 tothe retailer 104, the third intermediary user interface 222 isassociated with those aftermarket telematics devices 214. When aparticular aftermarket telematics device 214 is sold to a customer 106,the third intermediary user interface 222 is further associated with thecustomer 106, the retailer 104 and the transaction together. The datasource 200 has a record of such association and may provideauthentication of such association.

Aftermarket telematics devices 214 are devices that are adapted to beinstalled in vehicles 218 to provide different telematics features.Preferably, the aftermarket telematics devices 214 are connected to thevehicle data bus system such that the aftermarket telematics devices 214can provide features such as on-board diagnostics system, OBDII, engineperformance monitoring, and dashboard monitoring.

The aftermarket telematics devices 214 are configured to communicatewith external devices such as mobile device 206, 210, and 212 and/oreven directly with the server 202 and the data source 200. In someembodiments, the aftermarket telematics device 214 has the capacity tocommunicate with external devices such as mobile device 206, 210, and212 using wireless means such as Wi-Fi or Bluetooth. For example, theaftermarket telematics devices 214 can be paired with the first customermobile device 206 via Bluetooth. For some embodiments, the aftermarkettelematics devices 214 are also designed to communicate with otherexternal devices using wired connections such as USB cables. Short-rangewireless means such as Bluetooth is preferred because aftermarkettelematics devices 214 are sometimes installed behind the dashboard ofvehicles 218. In these situations, USB cables are less preferablebecause the aftermarket telematics devices 214 are often installedbehind the dashboard. For some other embodiments, the aftermarkettelematics devices 214 have the capacity to communicate with the server202 directly through long-range wireless means such as a 4G network.

In preferred embodiments, the aftermarket telematics device 214 furthercomprises an add-on option 220 that allows an add-on hardware 220 to beconnected with the aftermarket telematics device 214 to provideadditional telematics features. The add-on option 220 allows additionaltelematics features to be added to the aftermarket telematics device 214after the customer 106 purchases the aftermarket telematics device 214.For example, a particular aftermarket telematics device 214 is designedto provide a remote start feature. The customer 106 may purchaseadditional telematics features such as a GPS navigation feature throughbuying an add-on hardware 220 that contains the GPS feature.

After an aftermarket telematics device 214 is sold to a customer 106 andthe association among, for example, the manufacturer 100, thedistributor 102, the retailer 104, and the customer 106 are established,telematics applications 250 that are compatible with the aftermarkettelematics device 214 can then be delivered to the customer 106 indifferent ways. In some embodiments, once the telematics applications250 are delivered to the aftermarket telematics device 214, theapplications 250 will be stored on the cloud and be available fordownload using a unique identifier generated by the server 202 forfuture re-download.

In one scenario, a customer 106 purchases an aftermarket telematicsdevice 214 and decides to install the aftermarket telematics device 214to his vehicle 218 on his own. The particular aftermarket telematicsdevice 214 is equipped with a short-range wireless connectivity. Uponthe customer's 106 request, the data source 200 sends a first customeruser interface 204 to the customer's mobile device 206, which is thecustomer's 106 smart phone 206 in this scenario. After the firstcustomer user interface 204 is installed in the smart phone 206, thecustomer 106, using the first customer user interface 204, may manuallyselect a particular telematics application 250 from a plurality oftelematics applications stored in the data source 200 or make aselection based on the first customer user interface's 204recommendations. An association between the first customer userinterface 204 and the aftermarket telematics device 214 is authenticatedby the first customer user interface 204. Afterwards, the data source200 is adapted to respond to the requests from the first customer userinterface 204. In this particular scenario, the delivery of theparticular telematics application 250 is achieved through severalseparate steps. First, the data source 200 transmits the particulartelematics application 250 to the customer's smart phone 206. The datasource 200 also transmits an instruction that is adapted to cause thesmart phone 206 to re-transmit the particular telematics application 250from the smart phone 206 to the aftermarket telematics device 214. Assuch, the particular telematics application 250 is first downloaded tothe smart phone 206 and is temporarily stored in the smart phone 206.Then, when the customer 106 carries the smart phone 206 to a proximityto the aftermarket telematics device 214, such as when the customer 106is sitting inside the vehicle 218, the smart phone 206 pairs with theaftermarket telematics device 214 via the short-range wirelessconnectivity such as Bluetooth. Once the smart phone 206 and theaftermarket telematics device 214 are paired, the particular telematicsapplication 250 is transmitted from the smart phone 206 to theaftermarket telematics device 214 and is installed in the aftermarkettelematics device 214.

In a second scenario, a customer 106 purchases an aftermarket telematicsdevice 214, but the retailer 104 is responsible for installing theaftermarket telematics device 214 for the customer 106. As discussedabove, when the retailer 104 becomes an authorized retailer, themanufacturer 100 provides a second intermediary user interface 208 tothe retailer 104. Then when the aftermarket telematics device 214 issold, the retailer 104 uses a second intermediary mobile device 210 suchas a laptop computer to request a particular telematics application 250that suits the customer's need. The data source 200 is adapted torespond to the request from the second intermediary user interface 208.The retailer 104 connects his laptop computer 210 to the aftermarkettelematics device 214 via a USB cable. Upon proper authentication by thedata source 200 for an association between the second intermediary userinterface 208 and the aftermarket telematics device 214, the data source200 transmits the particular telematics application 250 to the laptopcomputer 210 and transmits an instruction to cause the laptop computer210 to re-transmit the particular telematics application 250 from thelaptop computer 210 to the aftermarket telematics device 214. After thetelematics application 250 is installed in the aftermarket telematicsdevice 214, the delivery of the telematics solution is complete.

In a third scenario, a customer 106 already has a functional aftermarkettelematics device 214 installed in his vehicle 218, but he wants toupgrade his aftermarket telematics device 214. The customer 106 prefersto ask the retailer 104 for assistance. An embodiment of the presentinvention provides a novel way to deliver a new telematics application250 without requiring the customer 106 to drive his vehicle 218 back tothe retailer 208. In this particular scenario, the data source 200, theaftermarket telematics device 214, the first customer user interface204, and the second intermediary user interface 208 have already beenassociated together and authenticated by the methods discussed above.The first customer user interface 204 shares the vehicle's 218information, the customer's 106 profile, and other information from theaftermarket telematics device 214 with the data source 200. The datasource 200 then shares the same information with the second intermediaryuser interface 208 so that the retailer 104 may review such informationusing the second intermediary user interface 208. As such, the retailer104 is able to select and request a particular telematics application250 for the customer 106 to upgrade the customer's 106 aftermarkettelematics device 214. The customer 106 does not have to physicallyreturn to the retailer 104 to perform the upgrade. Upon receiving therequest from the retailer 104, the data source 200 transmits theparticular telematics application 250 to the customer's 106 firstcustomer mobile device 206 instead of to the second intermediary mobiledevice 210 that is possessed by the retailer. The server 202 alsotransmits an instruction that is adapted to cause the first customermobile device 206 to re-transmit the particular telematics application250 to the aftermarket telematics device 214. In other words, theparticular telematics application 250 is first transmitted to thecustomer's 106 mobile device 206 upon the retailer's 104 remote request,and then re-transmitted to the aftermarket telematics device 214. There-transmission of the telematics application 250 may occur when thefirst customer mobile device 206 is paired with the aftermarkettelematics device 214 using a short-range wireless connection such asBluetooth or when the first customer mobile device 206 is connected tothe aftermarket telematics device 214 via a USB cable. Alternatively, ifthe aftermarket telematics device 214 has a long-range wireless capacitysuch as 4G-network connectivity, the server may deliver the particulartelematics application 250 selected by the retailer 104 directly to theaftermarket telematics device 214. As such, the delivery of theparticular telematics application 250 can be achieved when the retailer104 is away from the customer's 106 vehicle 218.

In a fourth scenario, the customer 106 also wants to upgrade hisaftermarket telematics device 214, but the telematics feature that hedesires requires an upgrade of the hardware. For example, theaftermarket telematics device 214 only supports remote startfunctionality, but the customer 106 wants to add a GPS navigation systemto his vehicle 218. In this case, the customer 106 first purchases apiece of add-on hardware 220 from the retailer 100 and connects theadd-on 220 to the aftermarket telematics device 214. As the additionalhardware is provided to the customer 106 as an add-on, the installationis much simpler than the installation where the customer has to purchasea new telematics device. It simply requires the customer to plug in theadd-on 220 to the aftermarket telematics device 214. After the add-on isconnected, the customer 100 may select a particular telematicsapplication 250 for the add-on hardware 220 manually or using the firstcustomer user interface's 204 recommendations. Alternatively, thecustomer 100 may ask the retailer 104 for assistance and the retailermay request the delivery of a particular telematics application 250 tothe aftermarket telematics device 214 as discussed above.

While only several scenarios are discussed above, those skilled in theart would understand that the ways to deliver a telematics solution isnot limited to the explicit discussions of the above scenarios.Different ways of delivering telematics solutions can also be thecombination of different scenarios.

Now referring to FIG. 3, an illustrative representation of anaftermarket telematics device 214 installed in a vehicle 218 ispresented. The aftermarket telematics device 214 is installed in thecentral console of the vehicle 218 behind the radio 302. The aftermarkettelematics device 214 provides different telematics features such asremote start and monitoring of the vehicle information. A customer 106,who is the driver, can control the aftermarket telematics device 214through the vehicle 218, such as by using the radio or the buttons onthe steering wheel. Additionally, the customer 106 can control theaftermarket telematics device 214 using the first customer userinterface 204 installed in the first mobile device 206. The driver mayalso request delivery of any particular telematics applications 205using the first customer user interface 204.

Now referring to FIG. 4, it represents a first customer user interface204 in accordance with some embodiments of the present invention. Thefirst customer user interface 204 provides a menu of different optionsfrom which customers 106 may choose. In the particular embodiment shownin FIG. 4, the first customer user interface 204 contains featuresincluding Configuration Manager, Product Categories, Sales Support,Account Manager and Aftermarket Telematics Device Options.

The drawings in FIG. 5 represent a configuration feature 500 of the userinterfaces 204, 208, and 222 in accordance with some embodiments of thepresent invention. In one embodiment, the configuration feature 500could be selected from the first customer user interface 204 shown inFIG. 4 under the Configuration Manager option. The configuration feature500 allows the customer 106 or any intermediaries 102 or 104 toconfigure their user interfaces 204, 208, and 222 and the aftermarkettelematics device 214. As shown in step 550, the configuration feature500 provides two different ways, VIN scanning 502 and vehicle lookup504, to configure the user interface and the aftermarket telematicsdevice. Using the VIN scanning 502 as shown in step 552 and 554, theuser interfaces directly scan the vehicle identification number (VIN) ofthe vehicle 214. The VIN scanning 502 also allows users to manuallyinput the VIN into the interface. After the VIN is scanned or input, theuser interface transmits the VIN to the server 202 to determine thevehicle's 218 information such as the vehicle's make, model, year, trim,and gearbox and automatically displays and associate the vehicleinformation with the user interface and the aftermarket telematicsdevice.

Alternatively, users may select the vehicle 218 manually by using thevehicle lookup feature 504 as shown in step 556. The users may findtheir vehicles 218 by narrowing the search result using the vehiclemake, year, model, and/or trim. Once the vehicle is located, the vehicleinformation will be displayed and associated with the user interface andthe aftermarket telematics device.

The configuration feature 500 can be done by the customer 106 or by anyof the intermediaries 102 or 104 when they sell or install theaftermarket telematics device 214 for the customer 106. Once the vehicleinformation is configured, the first customer user interface 204, thesecond intermediary user interface 208, and the third intermediary userinterface 222 will contain the particular vehicle's 218 information forthe particular customer 106 that is associated with the particularaftermarket telematics device 214.

FIG. 6 shows different options for customer 106 to select differenttelematics applications 250 in accordance with some embodiments of thepresent invention. In one embodiment, the options are a consumerprofiler tool 600, compatible products 602, and special offers 604.

FIG. 7 represents the customer profiler tool 600 in accordance with anembodiment of the present invention. The first customer user interface204 is adapted to collect information such as different searchparameters from customers 106. The first customer user interface 204should already have the vehicle information after the configurationsteps shown in FIGS. 4 and 5. In the customer profiler tool 600, thefirst customer user interface 204 requires customers 106 to input theiremail and allows the customers 106 to input additional information suchas their name, telephone numbers and address. Then on the next page 702,the customer profiler tool 600 continues to collect the customers' 106profile information such as their gender, age, ZIP code, mobile device206, and the mileage of their vehicle 218. The customer profiler tool600 also allows the customers 106 to input advanced search parameters.For example, in the additional search filter 704, the customer 106 maytell the first customer user interface 204 whether their vehicle 218 hascertain features such as navigation, hands free, remote starter, back-upcamera, and/or road side assistance.

FIG. 8 continues to represent the customer profiler tool 600 inaccordance with an embodiment of the present invention. The firstcustomer user interface 204 transmits the data input by the customer 106to the data source 200. Based on the information collected during thesteps shown in FIG. 7, the first customer user interface 204, workingwith the data source 200, analyzes the data and generates a user profilethat will recommend different telematics applications 250 selected fromthe plurality of different telematics applications stored in the datasource 200 to the customer 106. The recommended result is shown as thesearch results as shown in FIG. 8. The search result will be displayedby supported vehicle features first and then by most suitable featuresfor the customer 106 based on the search parameters collected. As shownin FIG. 8, the first customer user interface 204 lists telematicsapplications 250 that are compatible with the customer profile. Thecustomer 106 may select any of the telematics applications 250 listedand have the telematics applications 250 to be delivered to theiraftermarket telematics device 214.

In some embodiments, a cloud services environment is setup to enhancethe search and recommended results. This is achieved by crossreferencing the user's input with statistics that include vehiclewarranty status and location-based variables such as crime rates,climate patterns, fuel costs, average income, and legal driving age inorder to return potential features of interest. The data source 200analyzes the customer profile information collected and the statisticscross-referenced using fuzzy logic and provides proper recommendationsto the customer 106. Telematics solutions such as, but not limited to,remote start, security, telematics GPS tracking, Geo fence, speedalerts, road side assistance, DTC notifications, radio replacementoptions, custom gauges, and etc. are all available as potential results.

Through the customer profiler tool 600, embodiments of the presentinvention provide an interactive point of sales tool for both thecustomers 106 and the retailers 104 to determine the most suitablesolution for a particular vehicle 218 based on the customer'spreference. This provides an individualized solution for each customerbased on his or her needs. The customer profiler tool 600 providesrecommended telematics applications 250 based on the vehicle conditionand the customer's lifestyle. As such, embodiments of the presentinvention are able to deliver telematics solutions that are best suit tothe customer's situation by focusing on the features that may be ofinterest to the customer based on the profile data provided.

For example, when a customer 106 inputs a ZIP code that has a high crimerate, the customer profiler tool 600 will analyze the ZIP code andrecommend security features such as remote start and GPS tracking to thecustomer. When another customer 106 inputs a ZIP code that has a highhousehold income and the vehicle 218 is identified as a luxuriousvehicle, the customer profiler tool 600, using a fuzzy logic generator,will recommend premium telematics applications 250 that provide betterservices.

In another example according to an embodiment of the present invention,for example, when a middle-aged driver who drives a minivan, who has twoteen drivers, and who drives long miles per year in a cold area inputshis/her profile information, the customer profiler tool 600, using afuzzy logic generator, will recommend features such as remote starters,over-speed notifications and DTC (dynamic traction control)notifications to the customer. In yet another example, when a youngperson who drives a new sport car and lives in an area with relativelyhigh crime rate input his or her zip code, then the customer profilertool 600 will recommend features such as premium 2-way LCD remote startand security systems, smart phone alarm notifications and radioreplacements with virtual gauges.

The customer profiler tool 600 can be used with or without anaftermarket telematics device 214 already installed in the vehicle 218.If the customer 106 already has an aftermarket telematics device 214installed, after the customer 106 selected a particular telematicsapplication 250 recommended by the customer profiler tool 600, theserver 202 will deliver the particular telematics application 250 to theaftermarket telematics device 214. If the customer 106 does not have anaftermarket telematics device 214 already installed in the vehicle 218,then the customer 106 first selects the proposed telematics feature thatthey are interested in purchasing. The first customer user interface 204will then provide a list of local retailers 104 from which the customer106 can select to purchase the aftermarket telematics device 214. Thecustomers' profile, information, and selection will also be sent toserver 202 and be pushed to local retailers 104 for the retailers 104 tofollow up with the customer 106.

Referring back to FIG. 6, besides the customer profiler tool 600,customers 106 or retailers 104 may choose different telematicsapplications 250 using compatible products 602 or special offers 604.Compatible products 602 sort different telematics applications 250 thatthe aftermarket telematics device 214 can use by categories. Customers106 may opt to search by main categories such as remote start, security,telematics, or audio. Once a category is selected, the user may entervehicle make, model, and year to view compatible telematics solutions.Customers 106 can also select the product of interest and build asolution by selecting the desired control options and features. Once asystem is built, the first customer user interface 204 will display ademonstration on how the system will work through a virtual reality tourby displaying the vehicle image along with a control option image. Thecustomers 106 can then navigate through the demonstration to decidewhether it is the telematics solution that they want. If a desiredsystem is built, the customers' profile, information, and selection willbe sent to server 202 and be pushed to local retailers 104 for theretailers 104 to follow up with the customers 106.

Another option shown in FIG. 6 is the special offers 604. It recommendstelematics applications 250 that are currently in promotion to thecustomers 104 or retailers 104. In one embodiment, the first customeruser interface 204 will recommend only applications that are compatiblewith the vehicle 218 based on the vehicle information configured in thesteps shown in FIGS. 4 and 5.

The first customer user interface 204 provides an in-applicationpurchase feature. Once customers 106 have decided to purchase aparticular telematics application 250, the first customer user interface204 will display a transaction manager 810 for customers 106 to completethe transaction, as shown in FIG. 9. The transaction manager 810displays the price and other check-out information for the customers andwill prompt a series of fillable forms for customers 109 to input theirpayment information such as their credit card information. Once paymentis confirmed, an installation-pairing key 816 will be provided to thecustomer 109 for the installation of the particular telematicsapplication 250 into the aftermarket telematics device 214.

A rental feature is also provided in some embodiments. If a customer 106is interested in a particular telematics application 250 but he has notyet purchased the application 250, an option to rent the telematicsapplication 250 is available in some scenario. The rental feature willallow the customer 106 to try the application 250 for a limited timewithout committing to purchasing a permanent license. At the end of therental period, the particular telematics application 250 will goinactive and the customer 106 may purchase a full license at anadditional cost, extend the rental, or continue to use the telematicsdevice 214 using other telematics applications 250 without using theexpired trial application. This rental feature is also available for acustomer who has purchased an application to share the application withhis friend by providing a trial period to the friend.

FIGS. 10 and 11 illustrate a configuration manager 920 that allows thecustomers 106 to configure the particular telematics applications 250,which are installed in the aftermarket telematics device 214. Theconfiguration manager 920 can be used to configure the particulartelematics applications 250 before or after the applications 250 areinstalled in the aftermarket telematics device 214. The configurationmanager 920 provides different preference choices for the customers 106and also provide authentication among the telematics applications 250,the aftermarket telematics device 214, and the first customer userinterface 204, as shown in steps 964 and 965. The configuration manager920 authenticates the association between the user interface and thetelematics device 214 in steps 922 and 924 using the process asdiscussed above. The configuration manager 920 also allows customers 106to select installation guides and user owner manuals for their review,as shown in step 966.

In one embodiment of the present invention, a particular telematicsapplication 250 is configured before it is installed in the aftermarkettelematics device 214. After it is configured, the data source 200 willtransmit the particular telematics application 250 to the first mobiledevice 206 and causes the first customer user interface 204 tore-transmit the particular telematics application 250 to the aftermarkettelematics device 214, as shown in the flashing module at step 967.

In another embodiment, a particular telematics application 250 has beeninstalled in the aftermarket telematics device 214. The customer 106wants to re-configure the particular telematics application 250 usingthe configuration manager 920. In one particular scenario, there-configuration is minor and the first customer user interface 204 willcommunicate with the aftermarket telematics device 214 to change thepreferences in the telematics device 214. In another scenario, there-configuration is major and the server will transmit anothertelematics application 250 to the first mobile device 260 and the newtelematics application 250 will be installed into the aftermarkettelematics device 214 using the flashing module as shown in step 967.

While the previous discussion regarding FIGS. 4-11 focuses on theselection, purchase, delivery, and configuration of telematicsapplications 250 by the customers 106 using the first customer userinterface 204, those skilled in the art would understand that thefeatures shown in FIGS. 4-11 are also accessible to the intermediaries102 and 104 using their second intermediary user interface 208 and thirdintermediary user interface 222. As such, the intermediaries 102 and 104may also select and configure any particular telematics applications 250for their customers 106 at the point of sale using the features shown inFIGS. 4-11 and using the different ways of delivery of telematicsapplications 250 as discussed above. This allows intermediaries 102 and104 to configure the aftermarket telematics device 214 using the sameconfiguration options available to the customers 106.

The intermediaries 102 or 104 may also carry out the user registrationand authentication process for the customers 106 through their userinterfaces 208 or 222. During this process, the intermediaries 102 or104 may charge and bill the consumer directly, bypassing thein-application purchase model. In another embodiment, the intermediaries102 or 104 may also perform an upgrade of the customer's 106 aftermarkettelematics device 214 using their user interfaces 208 or 222.

After telematics applications 250 are installed and aftermarkettelematics devices 214 are functional, customers 106 may control andconfigure the aftermarket telematics devices 214 using their firstcustomer user interfaces 204. In some embodiments, a first customer userinterface 204 may first pair up with an aftermarket telematics device214 using wireless technologies such as Bluetooth. In a preferredembodiment, the device pairing is only possible when the vehicle'sdriver door is open and ignition is turned on for security reasons. Theserver 202 will authenticate the association of the first customer userinterface 204 and the telematics device 214 through unique identifier.

Referring now to FIG. 12, the first customer user interfaces 204 providein-application control features to allow customers 106 to, for example,adjust the volume and radio channel of their vehicle's radio. Otherin-application control features may include searching of points ofinterest and controlling of a GPS navigation system in the vehicle 218using the first customer user interface 204. The in-application controlprovides interactive features for the customers 106 to control theiraftermarket telematics device 214. In some embodiments, the developmentof telematics applications 250 is also open to third party developers108. This allows different people to invent innovative applications 250for the aftermarket telematics device 214 that are beyond what themanufacturer 100 originally provides. By simply downloading a newtelematics application 250, customer 106 can easily upgrade theiraftermarket telematics device 214 via in-application purchase throughthe first customer user interface 204 without having to go back to aretailer to perform an under-dash hardware upgrade. Even if a hardwareupgrade is required, it can be achieved by purchase an add-on hardwareas discussed above.

The control of the aftermarket telematics device 214 using the firstcustomer user interface 204 provides different interactive features forthe customers 106. One embodiment provides a multiple-user feature. Acustomer 106 has the option to create additional users under his or heraccount and assigns access rights to restrict access to certainfeatures. For example, different accounts can be created in aparent-child hierarchy. A parent account is able to create and deleteadditional users and restrict features such as engine runtime andsecurity features when the vehicle is being operated by a smartphoneunder a child account. Additionally, the parent account is capable ofgranting and restricting child-account users to access only or startonly specific vehicles on the account assigned to the child accounts.

Another embodiment provides a car-share feature. The car-share featureallows a customer 106 to assign trusted keys and set temporaryparameters such as limitations and alerts for a user-programmed periodof time or until such keys are cancelled by the customer 106. With thecar-share feature turned on, the owner of the vehicle 218 can set up atemporary authorized user that is authorized to drive the car. The ownersets up a car share profile with an email address of the temporarydriver. The temporary driver will then use the email address and aspecifically generated identifier, such as a password, to login to hisor her own first customer user interface 204 and unlock the vehicle 218.When the temporary driver unlocks the vehicle 218, the owner of thevehicle 218 can configure the vehicle 218 without the need of aphysically registered key being present in the vehicle.

In yet another embodiment, the first customer user interface 204provides a keyless feature. This is a feature that is compatible withvehicles that are equipped with push-to-start ignition systems. Thisfeature allows customers 106 to start the engine of the vehicle 218without requiring the OEM keyless entry fob present in the car. When thecustomer 106 carries a mobile device 206 with the first customer userinterface 204 installed, the first customer user interface 204 will pairwith the telematics device 214 and authenticate the ownership of thevehicle 218. This feature essentially replaces the necessity of havingto carry a keyless entry fob. When the customer 106 leaves the immediateproximity of the vehicle 218, the aftermarket telematics device 214 willshut the engine off and lock the doors automatically. For valet parting,the customer 106 may gain access of the vehicle 218 to the valet parkingpersonnel using the car-share feature as discussed above.

In yet another embodiment, the aftermarket telematics device 214monitors the vehicle's diagnostic information such as the engine andtransmission conditions. The first customer user interface 204 will beable to recommend a preferred service center in the customers' areabased on the customers' preferences and the diagnostic information. Thefirst customer user interface 204 will be able to generate an email thatwill send useful information about the vehicle 218 to the servicecenter.

FIG. 13 illustrates the intermediary user interface 208 and 222 featuresthat are available for the intermediaries 102 and 104. The intermediaryuser interfaces 208 and 222 provide features such as Product Manager980, SKU Manager 982, and Account Manager 984 for intermediaries 102 and104 to manage their inventory and transaction records. These featuresensure that all revenue from the in-application purchases of thecustomers are allocated properly among the intermediaries. Using thethird intermediary user interface 222, the third intermediary 102, forexample, a distributor, may use the Account Manager 984 to add or removesecond intermediaries 104, such as retailers. When a second intermediary104 makes sales of an aftermarket telematics device 214 to a customer106, a transaction record that is associated with the particularaftermarket telematics device 214, the customer 106, the retailer 104,and the distributor 102 will be generated. As such, the server 202, theretailer 104 and the distributor 102 will have a record of the purchase.If the customer 106 performs an in-application purchase, a transactionrecord that is associated with the retailer 104 and the distributor 102will be generated. As such, the retailer 104 and the distributor 102 mayreceive a share of the revenue based on this in-application purchase.Likewise, if the customer 106 purchases an add-on component 220 anddownload a telematics application 250 for the add-on component 220, asimilar transaction record that is associated with the retailer 104 andthe distributor 102 will also be generated.

Those of skill would further appreciate that the various illustrativelogical blocks, configurations, modules, and algorithm steps describedin connection with the embodiments disclosed herein may be implementedas electronic hardware, computer software, or combinations of both. Toclearly illustrate this interchangeability of hardware and software,various illustrative components, blocks, configurations, modules, andsteps have been described above generally in terms of theirfunctionality. Whether such functionality is implemented as hardware orsoftware depends upon the particular application and design constraintsimposed on the overall system. Skilled artisans may implement thedescribed functionality in varying ways for each particular application,but such implementation decisions should not be interpreted as causing adeparture from the scope of the present disclosure.

The foregoing description of the embodiments of the present inventionhas been presented for the purpose of illustration and description. Itis not intended to be exhaustive or to limit the invention to theprecise form disclosed. Many modifications and variations are possiblein light of the above teachings. The numerical values described in thedescription are only for illustration purpose and should not beunderstood as limiting the invention to the precise numbers. It isintended that the scope of the present invention not be limited by thisdetailed description, but by the claims and the equivalents to theclaims appended hereto.

I claim:
 1. A method for providing a plurality telematics applicationsto an aftermarket telematics device installed in a vehicle, the methodcomprising: providing a platform capable of storing said plurality oftelematics applications, wherein said platform is linked to a cloudserver; providing a first user interface to a customer; providing asecond user interface to an intermediary; authenticating an associationbetween said first user interface and said aftermarket telematics devicethrough a first authentication process; authenticating an associationbetween said second user interface and said aftermarket telematicsdevice through a second authentication process; receiving userinformation from said first user interface including afirst-user-requested update for said aftermarket telematics deviceincluding new telematics applications from said plurality of telematicsapplications; transmitting said user information to said second userinterface; providing said second user interface an option to select asecond-user-accepted update from said plurality of telematicsapplications; transmitting said second-user-accepted update to saidfirst user interface; and, transmitting a command to said first userinterface to control and configure said aftermarket telematics devicebased on said second-user-accepted update.
 2. The method of claim 1,further comprising: adapting said first user interface to be installedon a mobile device.
 3. The method of claim 1, further comprising:providing said platform to developers to develop and upload saidtelematics applications to said cloud server.
 4. The method of claim 1,further comprising: providing a profiling interface associated with saidfirst user interface to collect said user information.
 5. The method ofclaim 1, further comprising: recommending a telematics application fromsaid plurality of telematics applications to said customer from saiduser data.
 6. The method of claim 2, further comprising: providing saidfirst user interface an adaptation to cause said mobile device totransmit said telematics applications to said aftermarket telematicsdevice via a short-ranged protocol when said mobile device is inproximity to said aftermarket telematics device.
 7. The method of claim1, further comprising: providing an installation procedure so that saidfirst authentication process can only be initiated when said aftermarkettelematics device has detected that a door of said vehicle is open andan ignition of said vehicle is turned on.
 8. The method of claim 1,further comprising: providing said first user interface an adaptation togenerate a transaction record after said telematics applications havebeen transmitted to said aftermarket telematics device.
 9. A telematicsdevice system for vehicles, comprising: an aftermarket telematics deviceadapted to be installed in a vehicle, said aftermarket telematics devicecompatible with a plurality of telematics applications; a first userinterface adapted to communicate with said aftermarket telematic device,said first user interface configurable to be associated with saidaftermarket telematics device through a first authentication process; asecond user interface adapted to communicate with said aftermarkettelematic device, said second user interface configurable to beassociated with said aftermarket telematics device through a secondauthentication process; a data source adapted to store said plurality oftelematics applications, communicate with said first and second userinterfaces, and authenticate said first and second authenticationprocesses; wherein said data source is adapted to receive userinformation from said first user interface; said second user interfaceis adapted to receive said user information from said data source; saidsecond user interface is adapted to select a second-user-accepted updatefrom said plurality of telematics applications and instruct said datasource to transmit said second-user-accepted update to said first userinterface; and, said first user interface is adapted to receive saidsecond-user-accepted update and to control and configure saidaftermarket telematics device based on said second-user-accepted update.10. The telematics device system of claim 9, wherein said first userinterface is installed on a mobile device.
 11. The telematics devicesystem of claim 9, wherein said user data includes afirst-user-requested update for said aftermarket telematics deviceincluding new telematics applications from said plurality of telematicsapplications.
 12. The telematics device system of claim 9, wherein saidfirst user interface is adapted to control and configure saidaftermarket telematics device via a short-ranged protocol after saidfirst and second authentication processes.
 13. The telematics devicesystem of claim 9, wherein said aftermarket telematics device can beadapted to different telematics application features.
 14. The telematicsdevice system of claim 9, wherein said first user interface is adaptedto collect information from a user and, based on the informationcollected, generate a profile that recommends telematics applications tosaid user.
 15. The telematics device system of claim 9, wherein saidfirst user interface is adapted to communicate with a third party datasource associated with a developer application program interface thatallows developers to develop telematics applications compatible withsaid aftermarket telematics device.
 16. The telematics device system ofclaim 10, wherein said first user interface is adapted to cause saidmobile device to transmit said particular telematics application to saidaftermarket telematics device via said short-ranged protocol when saidmobile device is in a proximity to said aftermarket telematics device.17. The telematics device system of claim 9, wherein said authenticationprocess that associates said first user interface with said aftermarkettelematics device can only be initiated when said aftermarket telematicsdevice has detected that a door of said vehicle is open and an ignitionof said vehicle is turned on.
 18. The telematics device system of claim9, wherein said first user interface is used by an intermediary, aftersaid particular telematics application is delivered, said first userinterface is adapted to generate a transaction record that is associatedwith said intermediary.
 19. The telematics device system of claim 9,further comprising: a third user interface adapted to communicate withsaid data source.
 20. The telematics device system of claim 19, whereinsaid third user interface is adapted to communicate with saidaftermarket telematic device, said third user interface configurable tobe associated with said aftermarket telematics device through a thirdauthentication process.